home *** CD-ROM | disk | FTP | other *** search
- {\rtf0\ansi{\fonttbl\f0\fnil Times-Roman;\f2\fmodern Courier;\f1\fswiss Helvetica;}
- \paperw11760
- \paperh7200
- \margl120
- \margr120
- {\colortbl\red0\green0\blue0;}
- \pard\tx960\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600\f0\b0\i0\ul0\fs28 otool corefile \
- \
- Q: Now that all core files are dropped in /cores (as of release 2.0), how do I tell what application dropped a particular one?\
- \
- A: It's really easy — use
- \i otool -c <corefile>
- \i0 . It prints out the argv[] and envp[] that are on the stack. Once in a while, it doesn't work and doesn't print anything. \
- \
-
- \f2\fs24 % otool -c /cores/core.123\
-
- \fc0 Argument strings on the stack at: 0x4000000\
- ./testprogram\
- HOME=/Net/mymachine/someone\
- SHELL=/bin/csh\
- TERM=vt100\
- USER=someone\
- PATH=.:/usr/ucb:/bin:/usr/bin:/LocalApps:/NextApps:/usr/local/bin\
- Workspace=Workspace$1890247798\
- VISUAL=/usr/ucb/vi\
- %\
-
- \f0\fs28 \
- The core file also will have an extension that was the process number for the program when it was running. But that isn't all that helpful.
- \f2\fs24 \
-
- \f0\fs28 \
- QA558\
- \
- Valid for 2.0\
- \
-
-